Selective interrupt delivery to multiple processors having independent operating systems

ABSTRACT

A method of and apparatus for selective delivery of an interrupt to one of multiple processors having independent operating systems is described. The interrupts are generated from various platform devices in the computer system. Depending on the mode of operation of the system, a controller is configured to deliver interrupts to a co-processor when the host processor is off, without turning on the host processor. The interrupt may be delivered to the correct processor using wither a bus-based message or a dedicated interrupt line.

REFERENCE TO RELATED APPLICATION

[0001] This application is a continuation of application Ser. No. 09/676,463 filed Sep. 29, 2000.

FIELD OF THE INVENTION

[0002] The present invention relates to the field of computer systems and, in particular, to the operation of computer systems having multiple independent processors.

BACKGROUND OF THE INVENTION

[0003] Computer systems typically include various platform devices (e.g., disk drive) that operate under the control of a central processing unit (CPU). During operation of the computer system, interrupts are generated by these platform devices and transmitted to the CPU in order to communicate with the CPU.

[0004] Over the last few years, there have been many advances in computer system technology. These advances have lead to the development of computer systems having multiple processors to support additional and/or enhanced computing features. FIG. 1 illustrates, for example, one type of computer system that uses a co-processor in conjunction with a host CPU to perform complex mathematical operations. In such systems, the processors are under the control of a single operating system (OS). The use of single operating system, however, may limit the flexibility of the computer system.

[0005] Other advances in computer system technology have led to the development of battery-powered portable computers (e.g., laptop or notebook style computers, hand-held computers, etc.) that are implemented with high-speed processors similar to those implemented in desktop computers. Some of these portable computers may also include multiple processors. In order to conserve power in these systems, one or more of the processors may be placed in a low power mode, referred to as a “sleep mode” or “Limited ON” mode, when not in active use.

[0006] One problem with such a system is that the co-processor is not independent of the host CPU and, thus, cannot operate when the system is asleep. Therefore, the co-processor in the computer system will not be able to access system resources when the host processor is shut-down. In addition, when an interrupt is transmitted by a platform device, the interrupt is received by all the processors in the system including those that are not currently running or intentionally sitting idle. Such a configuration may lead to inefficiencies in the computer system. For example, a system operating with host CPU turned off may respond by waking up the host CPU upon receipt of an interrupt and, thereby, undesirably increase the power consumption of the system.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:

[0008]FIG. 1 illustrates a prior art computer system having multiple processors running a common operating system with a common communication bus.

[0009]FIG. 2 illustrates one embodiment of a computer system having multiple processors running independent operating systems.

[0010]FIG. 3 illustrates an alternative of a computer system having multiple processors running independent operating systems.

[0011]FIG. 4 illustrates another embodiment of a computer system having multiple processors running independent operating systems.

[0012]FIG. 5 is a flow chart illustrating one embodiment of an interrupt delivery method.

[0013]FIG. 6 illustrates one embodiment of control logic of a controller.

[0014]FIG. 7 is a state diagram illustrating one embodiment of the state machine of a controller.

DETAILED DESCRIPTION

[0015] In the following description, numerous specific details are set forth such as examples of specific operating systems, components, machine readable medium, etc. in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that these specific details need not be employed to practice the present invention. In other instances, well known components or methods have not been described in detail in order to avoid unnecessarily obscuring the present invention.

[0016] Thus, a machine readable medium includes any mechanism for storing or transmitting information in a form (e.g., software) readable by a machine (e.g., a computer). For example, a machine readable medium includes read only memory (ROM); random access memory (RAM); magnetic disk storage medium; optical storage medium; flash memory devices; electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.); etc.

[0017] The method and apparatus described herein may be implemented with a computer system having two processors, as illustrated by the accompanying figures. It should be noted, however, that the description of the method and apparatus in relation to a computer system having a host processor and a co-processor is only for illustrative purposes and is not meant to be limited only to a computer system having two processors. In an alternative embodiment, other numbers of processors may be used.

[0018] In one embodiment, the computer system may include a first processor coupled with a controller through a first bus and a second processor coupled with the controller through a second bus. The second processor (e.g., a co-processor) operates with an operating system independent from the operating system of the first processor (e.g., a host processor). The second processor is coupled with the controller through a bus different than that used to couple the first processor with the controller. The method of interrupt delivery may include receiving an interrupt request by either the first processor or the second processor based on the mode of operation of the computer system. The interrupt being received by the first processor uses a communications link different than the second processor.

[0019]FIG. 2 illustrates one embodiment of a computer system having multiple processors running independent operating systems. Computer system 200 includes a processor 210, memory control hub (MCH) 220, an input/output control hub (ICH) 230, platform devices 240, co-processor 250, and buses 261-264. Buses 261-264 carry data and addresses to the various components in computer system 200.

[0020] The MCH 220 controls operations between processor 210 and memory devices (not shown), for examples, a graphics controller and a random access memory (RAM). The ICH 230 controls operations between processor 210 and platform devices 240. Platform devices 240 may be, for example, a disk drive and a universal serial bus (USB) device. In another embodiment, the MCH 220 and the ICH 230 may be integrated into a single component.

[0021] Computer system 200 requires at least a main operating system in order to function. The main operating system may be stored on one of the platform devices 240 of computer system 200. When computer system 200 boots (i.e., is started), a set of basic input/output start up (BIOS) routines stored in memory are executed by processor 210 of the system and subsequently loads the main operating system of computer system 200.

[0022] Computer system 200 also includes a co-processor 250. Co-processor 250 is coupled to ICH 230 using a separate bus 261 than the bus for processor 210, and co-processor 250 is configured to operate with an independent operating system from that of processor 210, referred to as a mini OS. The mini OS of co-processor 250 may be loaded at approximately the same time as the main OS for processor 210. In one embodiment, for example, the main OS may be a Microsoft Windows™ OS and the mini OS may be a real time operating system (RTOS) such as QNX available from QNX Software Systems Ltd. of Canada and Precise/MQX available from Precise Software Technologies Inc. of Canada. In an alternative embodiment, processors 210 and 250 may operate with other operating systems.

[0023] Computer system 200 may be configured to operate in various modes. In one embodiment, computer system 200 has three modes of operation: Full ON, Limited ON, and Listen. In Full ON mode, processor 210 and co-processor 250 are both on. In Limited ON mode, processor 210 is off and co-processor 250 is on and configured as the master device. In Listen mode, processor 210 is off and co-processor 250 is partially on and configured as the master device. During the transition from the Full ON mode to the Limited ON mode, either hardware or software may be used to configure ICH 230 into the appropriate mode.

[0024] In one embodiment, in the Full ON mode, processor 210 may function as a master device with co-processor configured as a slave device, such as a personal computer interface (PCI) device, in the system. A PCI device is well known in the art, accordingly, a detailed discussion is not provided.

[0025] During operation of computer system 200, interrupt requests (IRQ) may be generated from one or more of platform devices 240 (e.g., IRQX, IRQY, and IRQZ). The IRQ is delivered from platform devices 240 to ICH 230 on signal line 264. However, an interrupt may also be generated from co-processor 250 and delivered to ICH 230 on bus 261. Depending on the mode of operation of computer system 200 at the time of the interrupts, ICH 230 delivers interrupts to either co-processor 250 or processor 210 using interrupt controller 235.

[0026] Interrupt controller 235 serves as an interface between platform devices 240 and processors 210, 250 in handling interrupt requests. For example, platform device 241 may toggle an IRQ line to signal an interrupt. Interrupt controller 235 accepts the interrupt request from platform device 241 and issues an interrupt request to, for example, processor 210 on a communications link 265. In one embodiment, communications link 265 is a dedicated interrupt line. On receiving the interrupt request from interrupt controller 235, processor 210 initiates an acknowledgement command on the host bus 263 when it is ready. The interrupt acknowledgement command requests the identification of the platform device 241 that sent the IRQ. Interrupt controller 235 sends an interrupt vector to processor 210 on bus 263 that identifies the requesting platform device 241 and a corresponding routine in processor 210 to handle the interrupt pending on platform device 241.

[0027] In one embodiment, interrupt controller 235 is a programmable interrupt controller such as the 8259 from Intel Corporation of Santa Clara, Calif. The 8259 may be used to handle operating systems such as the Microsoft Windows 95 operating system. In alternative embodiments, other programmable interrupt controllers and operating systems may be used.

[0028] In one embodiment, ICH 230 includes a state machine that operates to recognize that there may be a more than one possible master processor in computer system 200 and redirect an interrupt request to either processor 210 or co-processor 250 based on the system state. For example, the state machine may direct all requests to processor 210 when computer system 200 is in the Full ON mode and to processor 250 when computer system 200 is in the Limited ON or Listen mode discussed above. As such, ICH 230 is aware of the current mode of operation in computer system 200. In one embodiment, software may be used to program ICH 230 to know the current operating mode of computer system 200. In an alternative embodiment, ICH 230 may be hardwired to detect the mode of computer system 200 based on a signal state.

[0029]FIG. 7 is a state diagram illustrating one embodiment of the state machine of ICH 230. In state 710, the computer system is in Full On mode. If a sleep event is detected, the computer system determines whether a co-processor exists, step 711. If a co-processor does not exist, the computer system transitions to a low power mode and enters suspend state 715. Upon the occurrence of a wake event, the computer system transitions to Full On state 710.

[0030] If a co-processor is determined to exist at step 711, the computer system performs a transition to a low power mode and notifies the co-processor's mini OS of the transition, step 720. The mini OS performs housekeeping activities and initializes and saves the system state, step 730. The computer system is now in listen mode, state 740, and the interrupts get routed to the co-processor. If an event interrupt is detected, the co-processor wakes up the required platform devices to perform the required activity, step 745. The system goes into Limited On mode, state 750. Once activity is complete, the computer system's resources are shut-down, step 755, and the computer system returns to state 740.

[0031] Upon a system wake event interrupt, the mini OS performs housekeeping and restores the system state, step 760. The interrupts then get re-routed to the host processor, step 765. The system wake event is regenerated, step 766, and the computer system transitions to Full On mode, step 770.

[0032]FIG. 3 illustrates an alternative of a computer system having multiple processors running independent operating systems. The components of computer system 300 are similar to those of computer system 200 of FIG. 2 unless otherwise stated. In this embodiment, the interrupt controller 335 of ICH 330 may be an advanced programmable interrupt controller (APIC) such as the 82489DX from Intel Corporation of Santa Clara, Calif. An APIC may be used by operating systems such as the Microsoft Windows NT Operating System that allows more flexibility in interrupt handling. In an alternative embodiment, another APIC and operating system may be used.

[0033] ICH 330 is configured such that an interrupt message may be delivered on multiple buses (e.g., buses 361 and 366) that connect processors (e.g., processors 310 and 350) to ICH 330. When an interrupt is pending, platform device 341 sends an interrupt signal to APIC 335. In response, APIC 335 may issue an interrupt data packet to either processor 310 on bus 366 or processor 350 on bus 361. The use of bus 366 with APIC 335 enables not only the signaling of an interrupt, but also enables the identification of the particular platform device issuing the interrupt through the use of a data packet.

[0034] The targeted processor then uses the data packet to determine the address of the interrupt service routine. The targeted processor executes the interrupt service routine to process the interrupt.

[0035] ICH 330 is configured to recognize the that there may be a more than one possible master processor in computer system 300 and redirect an interrupt request to either processor 310 or co-processor 350 based on the mode of operation. In one embodiment, software may be used to program ICH 330 to know the current operating mode of computer system 300. In an alternative embodiment, ICH 330 may be hardwired to detect the mode of computer system 300 based on a signal state.

[0036] In yet another embodiment, interrupt controller 335 of ICH 330 may include both a PIC and an APIC with the APIC configured to issue interrupts to processors 310, 350 from either the PIC or directly from platform devices. In the embodiment where co-processor 350 is configured as a PCI device, interrupt controller 335 is configured to handle either PIC or PIC/APIC interrupts. A message signaled interrupt (MSI) mechanism may also be supported by ICH 330 which allows PCI devices to write to a register in ICH 330 as an equivalent of toggling an IRQ line.

[0037]FIG. 6 illustrates one embodiment of control logic of a controller. Control logic 630 may be implemented within an ICH 699 that, for example, includes both a PIC 672 and an APIC 673. ICH 699 includes a hublink interface 677 and a co-processor interface 671 for communication with a MCH and co-processor, respectively. Control logic 630 includes switches 637 and 638, and packetizer 639. Switch 638 is coupled to receive a signal from PIC 672 on line 631 and switch 637 is coupled to receive a signal from APIC 673 on bus 632. In one embodiment, if control signal 674 for switch 637 or 638 is high, interrupts are directed to a host processor on either line 665 or bus 666, corresponding to the use of PIC 672 and APIC 673, respectively. If the control signal 674 for switch 637 or switch 638 is low, interrupts are directed to a co-processor. Packetizer 639 converts either interrupt method into an interrupt message that the co-processor uses. Packetizer 639 is coupled to co-processor interface 671 with bus 676.

[0038]FIG. 4 illustrates another embodiment of a computer system having multiple processors running independent operating systems. The components of computer system 400 are similar to those of computer system 200 of FIG. 2, unless otherwise stated. In this embodiment, ICH 430 does not use a dedicated interrupt line or an APIC bus to communicate interrupts to processor 410. Rather, the interrupts are communicated to processor 410 via host bus 463. ICH 430 converts the IRQ into a memory write cycle and sends it upstream to host bus 463. Processor 410 snoops this address and accepts the interrupt.

[0039] The use of a separate bus for communication with a co-processor running a independent OS than a host processor is independent of the attachment point for the co-processor. Although FIG. 24 illustrate a co-processor coupled to the ICH, in alternative embodiments, the co-processor may be coupled to other components of the computer system. For examples, the co-processor may be coupled to the MCH, directly to the host processor or integrated with the host processor.

[0040] In an alternative embodiment, computer system 200 may be other types of computer systems, for examples, a desktop or server system. Moreover, the co-processors of FIGS. 2-4 above may be replaced with a gateway configured to access computer system resources in a manner to minimize costs. The gateway is a device that provides wide area network (WAN) or Internet access to a local area network. In one embodiment, the gateway may include a network card that may operate with, for examples, ADSL, cable modems, wireless modems, and home networking hardware.

[0041]FIG. 5 is a flow chart illustrating one embodiment of a method of interrupt delivery. The method discussed in relation to FIG. 5 is for an implementation of a co-processor coupled to an ICH in a computer system. In alternative embodiments, the method may be altered for the implementation of a co-processor attached to other components in the system.

[0042] In one embodiment, an ICH of a computer system determines a mode of operation of the computer system having a host processor and a co-processor operating with independent operating systems, step 510. The modes of operation may include, for example, a Full ON mode, a Limited ON mode, and Listen mode. In the Full ON mode, the host processor and the co-processor are both on. In the Limited ON mode, the host processor is off and the co-processor is on. In Listen mode, the host processor is off and the co-processor is in a low power mode with the co-processor configured as a master device waiting for a trigger event. In an alternative embodiment, the host processor may be configured as the master device.

[0043] The ICH is then placed in the appropriate mode, step 520. For example, during the transition from the Full ON mode to the Limited ON mode, software may be used to configure the ICH into the appropriate mode.

[0044] When an interrupt is pending, a platform device coupled to the ICH sends an interrupt signal to an ICH interrupt controller, step 530. In response, the ICH interrupt controller delivers the interrupt to one of the host processor and the co-processor based on the computer system's current mode of operation, step 540. In an alternative embodiment, the ICH interrupt controller may determine the destination processor after an interrupt is received from a platform device.

[0045] If the computer system is in Limited ON mode (or Listen mode with the co-processor configured as the master device), the ICH interrupt controller delivers the interrupt request to the co-processor on a bus line different than that used to communicate with the host processor, step 550. When the main OS is running in the system, all resources including the ICH interrupt controller may be under the control of the host processor running the main OS. As such, having the ICH interrupt controller re-directing interrupts to a co-processor occurs when the main OS is in a sleep mode (i.e., not running).

[0046] In an alternative embodiment, if there is a need to have some platform devices interrupt the co-processor while both the co-processor and the host processor are running, the ICH may first deliver the interrupt to the host processor's interrupt controller. The interrupt controller of the host processor services the interrupt on its software stack and then may interrupt the co-processor as needed through messaging. In such an embodiment, the co-processor and the host processors include protocols between them to handle these mechanisms.

[0047] On receiving the interrupt request from the ICH interrupt controller, the co-processor initiates an acknowledgement command when it is ready, step 560. The co-processor then runs a routine to handle the interrupt pending on the requesting platform device, step 570.

[0048] In one embodiment, the interrupt acknowledgement command requests the identification of the platform device that sent the interrupt request. The ICH interrupt controller then sends an interrupt vector to the co-processor that identifies the requesting platform device. In an alternative embodiment, the interrupt request includes the identification of the platform device that sent the interrupt request. In yet another embodiment, the ICH may be configured to detect the mode of operation before receipt of an interrupt request.

[0049] If the host processor is determined to be the destination processor, then the ICH interrupt controller delivers the interrupt request to the host processor on a bus line different than that used to communicate with the co-processor, step 580. The host processor is the destination processor in Full ON mode and in standby mode where a capable co-processor is not present.

[0050] On receiving the interrupt request from the ICH interrupt controller, the host processor initiates an acknowledgement command when it is ready, step 585. The host processor then runs a routine to handle the interrupt pending on the requesting platform device, step 590.

[0051] The computer systems described above in relation to FIGS. 2-4 may be a battery-powered portable computer system, for example, a laptop, notebook style computer, or hand-held device. By using different buses to delivery interrupt requests to multiple processors based on the mode of operation of the computer system, independent operation of the multiple processors is possible. This allows the co-processor to access system resources even when the processor containing the main OS is shut-down. As such, maximization of battery life in the portable computer system may be possible while still enabling use of some of the computer's functionality in a very low power mode (e.g., even when the screen is closed).

[0052] In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense. 

What is claimed is:
 1. A computer system, comprising: a first processor coupled with a controller through a first bus, the first processor operating with a first operating system; and a second processor coupled with the controller through a second bus, the second processor operating with a second operating system independent from the first operating system, wherein the controller directs an interrupt request to the second processor when the first processor is off.
 2. The computer system of claim 1, wherein the second processor is on.
 3. The computer system of claim 1, wherein the second processor is in a low power mode.
 4. The computer system of claim 1, wherein the first processor is a host processor and the second processor is a co-processor.
 5. The computer system of claim 1, further comprising a communication link between the controller and the first processor to send the interrupt request from the controller to the first processor when the first processor is on, the communication link being different than the second bus.
 6. The computer system of claim 5, wherein the communication link is a bus.
 7. The computer system of claim 5, wherein the communication link is a dedicated interrupt line.
 8. The computer system of claim 1, further comprising a platform device coupled to the controller to send the interrupt request to the controller.
 9. The computer system of claim 1, wherein the second operating system is a real-time operating system.
 10. The computer system of claim 1, wherein the first operating system is a general purpose operating system.
 11. A method of communication, comprising: determining a mode of operation using a controller; and directing an interrupt request from the controller to one of a first processor and a second processor based on the mode of operation, the first processor operating with a first operating system independent of a second operating system of the second processor, the interrupt directed to the first processor using a first communication link different than a second communication link used to direct the interrupt to the second processor.
 12. The method of claim 11, wherein the controller directs the interrupt request to the second processor when the mode of operation is a low power mode.
 13. The method of claim 12, further comprising maintaining the first processor in an off state.
 14. The method of claim 11, wherein the interrupt request is directed to the first processor using a dedicated signal line.
 15. The method of claim 11, wherein the interrupt request is direct to the first processor using a bus based interrupt delivery.
 16. A method, comprising: determining a mode of operation of a computer system; receiving an interrupt request by a controller from a platform device; directing the interrupt request to a co-processor when the computer system is in a low power mode; and directing the interrupt request to a host processor when the computer system is in a full power mode, the co-processor to operate independent of the host processor, the platform device not being the co-processor or the host processor.
 17. The method of claim 16, wherein the interrupt request is directed to the host processor using a first communication link different than a second communication link used to direct the interrupt to the co-processor.
 18. The method of claim 16, further comprising initiating an acknowledgement command when one of the co-processor and the host processor is ready to receive an interrupt.
 19. The method of claim 16, further comprising handling the interrupt pending on the requesting platform device.
 20. The method of claim 16, wherein the host processor has a first operating system independent from a second operating system of the co-processor.
 21. The method of claim 16, wherein the interrupt is directed to the co-processor without turning on the host processor.
 22. A machine readable medium having stored thereon instructions, which when executed by a processor, cause the processor to perform the following: determining a mode of operation of a computer system; receiving an interrupt request by a controller from a platform device; and directing the interrupt request by the controller to one of a first processor and a second processor based on the mode of operation, the second processor to operate independent of the first processor, the platform device not being the first processor or the second processor.
 23. The machine readable medium of claim 22, wherein the processor further performs the following: placing the computer system in the mode of operation; initiating an acknowledgement command when one of the first and the second processors is ready to receive an interrupt; and handling the interrupt pending on the requesting platform device.
 24. The machine readable medium of claim 23, wherein the interrupt request is sent to the first processor on a first communication link different than a second communication link used to direct the interrupt to the second processor.
 25. An apparatus, comprising: means for determining a mode of operation of a computer system; means for receiving an interrupt request by a controller from a platform device, wherein the controller is coupled to the platform device and a first and second processor, the platform device not being the first processor or the second processor; means for directing the interrupt request by the controller to one of the first processor and the second processor based on the mode of operation; and means for operating the second processor independent from the first processor.
 26. The apparatus of claim 25, further comprising means for handling the interrupt pending on the requesting platform device.
 27. The apparatus of claim 25, further comprising directing the interrupt request to the first and the second processors using different communication links.
 28. The method of claim 11, further comprising receiving an interrupt request by a controller from a platform device.
 29. A method, comprising: determining a mode of operation by a controller of a computer system; receiving an event interrupt by the controller from a platform device when a host processor is off and a co-processor is at least one of fully on and partially on; directing the event interrupt received by the controller to the co-processor on a first communication link; and waking up a second platform device by the co-processor to perform an activity required by the event interrupt, the platform device not being the co-processor or the host processor.
 30. The method of claim 29, further comprising: receiving an system wake event interrupt by the controller from a platform device when the host processor is off and the co-processor is at least one of fully on and partially on; waking up the host processor; and redirecting the system wake event interrupt received by the controller from the platform device to the host processor on a second communication link.
 31. The method of claim 29, wherein determining the mode of operation by the controller of the computer system comprises detecting the mode of operation before receiving the interrupt request by the controller from the platform device.
 32. The method of claim 29, further comprising: initiating an acknowledgement command by the one of the host processor and the co-processor when the one of the host processor and the co-processor is ready, wherein the interrupt acknowledgement command requests an identification of the platform device that sent the interrupt request; and sending an interrupt vector from the controller to the one of the host processor and the co-processor that provides the identification of the platform device.
 33. The method of claim 29, where in the mode of operation the host processor is off and the co-processor is at least one of fully on and partially on and the co-processor is configured to be a master device.
 34. The method of claim 29, wherein the host processor has a first operating system independent from a second operating system of the co-processor.
 35. The method of claim 29, wherein the interrupt request is directed to the co-processor without turning on the host processor.
 36. The method of claim 29, wherein the interrupt request is directed to the host processor using a dedicated signal line.
 37. The method of claim 29, wherein the interrupt request is direct to the host processor using a bus based interrupt delivery. 